chore!: remove excluded users from ListUsers response #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Will Vedder <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #87 +/- ##
============================================
+ Coverage 27.49% 27.72% +0.22%
+ Complexity 787 785 -2
============================================
Files 159 158 -1
Lines 5928 5862 -66
Branches 651 639 -12
============================================
- Hits 1630 1625 -5
+ Misses 4222 4161 -61
Partials 76 76 ☔ View full report in Codecov by Sentry. |
rhamzeh
approved these changes
Jun 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Removes
excluded_usersfrom the response of all SDKs as it was removed from OpenFGA with openfga/api#171.This feature was originally a well-intentioned way to communicate any negations that may exist on public-typed wildcard (e.g.
user:*) as a means of being abundantly clear about what auser:*result entails. However, as we discover more possible situations where excluded users could arise, we realize that we were making a premature decision about the API. We fully intend to re-add excluded_users at some point in the future but may or may not be a flattened list as previously implemented.Please note:
References
Review Checklist
main